Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Result
A legal serial order of the #7674 forward native graph from aliromman uses 2,106 snapshot banks, saving 319 against the fixed-order minimum of 2,425 in #7681. Including the shared paid-row accumulator and four scratch fields, the private reservation falls from 2,430 to 2,111 homes per occurrence, or from 38,880 to 33,776 over 16 disjoint occurrences.
This is a finite allocation certificate with a scoped proof of operator preservation. Among ready rows, the schedule chooses the one that will finish the most donors' remaining reads. Each row retains its exact coefficient list, charts, child and adapters. The new bank is reserved before the first read, all donors survive through child return, and all outputs survive until public installation. The peak is attained at event 3,022, token 94,904. Proof and contract · Generated receipt · Advance claim
Evidence and reproduction
The replay checks 7,643 row events, 9,144 assignments, 169,343 donor reads and 1,501 final outputs against the pinned forward graph. Independent owner counts confirm the peak. Both a live donor/result alias and the assignment restricted to 2,105 banks are rejected. The new schedule pays for all 30,580 full initialization/retirement services per occurrence. The conservative 16-occurrence reset allowance is 11,816,384.
Run from the repository root with any CPython 3.12 interpreter.
The certificate command writes the TSV to standard output. Both registered commands passed locally in 0.62 s each on macOS arm64. Output was
PASS_BANKED_NATIVE_ROW_ORDER 2106 banks, 2111 private homes, 169343 reads. The package and committed-byte, mode and source-history checks passed. The complete TSV hashes to16de610956122d9f2c68f05d955b5484a0ee31bf201b69546a092495bf97dd86.Limits and credit
The 2,106 lower witness applies to this order and this owner contract. A global schedule optimum and a concrete packed-tape implementation remain open. The proof uses the published row semantics and the five inherited framework assumptions. Physical child operators, the full caller, the selected cold replay and a formal proof were outside the local checks. There is no new κ.
This allocation was produced by Nick Petalas. aliromman posed the question and supplied the fixed-order allocation, fifteen pivots and field-level cost contract. SYLforge supplied the underlying word and caller. Clear1nsight supplied the public comparator encoding and digest. The package retains the original source notices. Credits and graph provenance
Related open work
Open next questions
CI notes
The PR carries the shared CI-doc and replay-gap sync used by other open PRs.
All six current-status tests, the historical replay-gap package and the bank allocation package passed locally at
ef52676eb20c252f5786f42a70ef0dd814400a03. The shared planning test on the base guide expectedmake frontier7000-verifyand foundmake frontier6030-verify. The same assertion appears in the #7681 plan failure. All three hosted checks passed atef52676eb20c252f5786f42a70ef0dd814400a03, including planning, the bank allocation replay and the historical replay-gap replay. CI run 44369322855